-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Resolve: update to new publisher #157
Resolve: update to new publisher #157
Conversation
…remove menu_style.qss file. Update pipeline with ResolveHost class changes.
- Renamed functions to use "ayon" instead of "pype" for consistency. - Added backward compatibility for old function names. - Updated marker handling in various plugins for Ayon integration.
… class names. Refactor Creator to ResolveCreator and PublishClip to PublishableClip for consistency. Remove unused imports and code related to LegacyCreator.
…utes and methods for clip creation. Improve GUI settings for shot hierarchy and renaming.
…project. Introduce plugin for collecting current project data and creating otio timeline. Refactor file extraction process for better representation handling.
- Updated function names for consistency and clarity - Renamed menu launcher functions to reflect the current context - Removed unnecessary variables and commented-out code in lib.py
…ndling. Adjust naming conventions for Ayon compatibility.
…ve plugins. Adjust imports accordingly.
Nice!
|
@@ -260,3 +263,138 @@ def on_pyblish_instance_toggled(instance, old_value, new_value): | |||
# Whether instances should be passthrough based on new value | |||
timeline_item = instance.data["item"] | |||
set_publish_attribute(timeline_item, new_value) | |||
|
|||
|
|||
class HostContext: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you add a docstring about what this does and what it tries to solve?
It seems overly complex, trying to manage 'data' that should really be INSIDE the project. Why do we need this global cache that also gets removed afterwards. What is this 'context'? Why does it contain 'instances' if it's not workfile related?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure where should be this comment on. It seems the code had changed a lot.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems to be on the right spot still. Basically, what is the HostContext
class and why do we need it? Would be good to have a docstring to describe its usage. Why couldn't we store this data within the project?
Task linked: OP-8066 Resolve: update to new publisher |
- Removed the function for loading stylesheets in the menu. - Refactored plugin creation logic to use new API methods and data structures.
server_addon/resolve/client/ayon_resolve/RESOLVE_API_v19.0B-build20.txt
Outdated
Show resolved
Hide resolved
…ed content related to previous versions.
- Refactored function names and descriptions for clarity - Added new function to export timeline otio files - Improved temporary directory handling for otio files
Adjusted get_otio_temp_dir to set timeline if not provided, throwing error if none found.
Co-authored-by: Roy Nieterau <[email protected]>
PR moved to ayon-resolve repository ynput/ayon-resolve#3 |
Note
Description is work in progress
Changelog Description
Resolve with adapted latest publisher tool.
Additional info
Adaptation of ynput/OpenPype#5709 (thanks @BigRoy for the kick-off!)
TODO:
?
- primary:
shot
- instance with hierarchy, future context data and attributes placeholder- secondary:
plate
,audio
,review
- instance with mediaTesting notes:
To be created